Open
Conversation
…e.yaml with volume configuration
- Created deploy/docker/openclaw/compose.yaml following n8n pattern
- Configured volume: openclaw_data mounted to /root/.openclaw
- Configured network: traefik-public with overlay driver
- Added Traefik labels for HTTP/HTTPS routing with WebSocket support
- Set port 18789 for OpenClaw Gateway
- Environment variables: NODE_ENV=production, TZ with Asia/Tokyo default
- All values use ${VAR:-default} pattern for configurability
- Replicas set to 1 (stateful service)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ructions Created comprehensive README.md for OpenClaw stack including: - Overview of OpenClaw capabilities - Environment variables (required and optional) - AI model API keys configuration - Channel integration tokens - Deployment methods (manual and GitOps) - External secrets configuration - Storage and network details - Access URLs for WebSocket Gateway - Verification and troubleshooting steps Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Exclude auto-claude tracking files from version control. The .auto-claude directory contains: - implementation_plan.json (local tracking) - build-progress.txt (local tracking) - VERIFICATION.md (local documentation) These files are for development workflow tracking only and should not be committed to the repository. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
QA feedback indicated that .doco-cd.yaml does not need to be updated for the openclaw stack. The entry has been removed. Fixes: - Remove openclaw stack registration from .doco-cd.yaml Verified: - grep confirms no openclaw entry remains in .doco-cd.yaml QA Fix Session: 1
…equested) Fixes: - Remove redundant deploy/docker/openclaw/.env file (codebase uses .common.env pattern) - Restore openclaw entry in .doco-cd.yaml (required by spec Success Criterion #2) Verified: - .env file removed from deploy/docker/openclaw/ - openclaw entry correctly added to .doco-cd.yaml with proper name and working_dir - Codebase pattern followed (no per-stack .env files like n8n) QA Fix Session: 0 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fixes: - Remove deploy/docker/openclaw/README.md file - Codebase pattern uses only compose.yaml per stack (no per-stack READMEs) - Matches existing stacks: n8n, warpgate, eval, etc. Verified: - README.md deleted from deploy/docker/openclaw/ - Directory now contains only compose.yaml - Matches codebase pattern for Docker stacks QA Fix Session: 1 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This task adds a new docker stack for OpenClaw, an AI agent tool that provides autonomous execution capabilities through a WebSocket-based Gateway interface. OpenClaw enables AI agents to interact with various platforms (Telegram, Discord, Slack) and execute commands with configurable security constraints. The stack will be deployed using Docker Swarm with Traefik routing, following the established patterns used by existing stacks in the codebase.